Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting
Using the DEBUGGER system handle in stand-alone mode
This technique is useful for running the Debugger as a tool started from one application to debug other applications. The invoking procedure runs the Debugger much like a subroutine, but it does not specify any procedure for the Debugger to run as its initial current procedure. You must run all procedures you want to debug from the Debugger after it starts by using the Run option on the Debug menu.
Invoking the Debugger as a tool of your application
![]()
To start the Debugger from the 4GL while blocking the invoking procedure:
In the following example, the procedure presents four execution options. The first three options invoke procedures. The fourth option invokes the
DEBUG( )method and blocks at the following statement (line 33) while the Debugger runs:
When the Debugger starts, you can open a procedure using File
Open and then run the procedure using Debug
Run.
As a result, while the invoking procedure waits on the blocked statement, the Debugger runs on its own, allowing you to control any other procedure that you start from it.
When you exit the Debugger, it returns control to the invoking procedure, which continues execution from the next statement (line 33 in the example). In stand-alone mode, you cannot otherwise access the invoking procedure until the Debugger returns control.
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |